-
Notifications
You must be signed in to change notification settings - Fork 45
Remove migrating section of FAQs #2860
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Conversation
Important Review skippedAuto reviews are disabled on this repository. Please check the settings in the CodeRabbit UI or the You can disable this status message by setting the ✨ Finishing touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
25e2591
to
5190f70
Compare
|
||
## Migration process <a id="migration-process"/> | ||
|
||
A typical migration from PubNub to Ably follows these steps: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can we change "Ably client libraries" to "Ably SDKs" please.
|
||
3. Migrate all your apps and servers to use Ably client libraries and terminate your old contracts. | ||
|
||
If you're interested in migrating from PubNub using protocol adapters, [get in touch](https://ably.com/contact). |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't think this is necessary in the docs considering the steps are outline here.
|
||
## Migration support <a id="migration-support"/> | ||
|
||
Ably helps customers migrate from other data streaming networks including PubNub and Pusher. Protocol adapters facilitate risk-free migration by allowing you to use existing protocols and client libraries while transitioning to Ably client libraries over time. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
"Client libraries" to "SDKs" when referring to our own here too please.
|
||
Protocol adapters offer an alternative method for connecting to Ably. The advantage to protocol adapters is that they require fewer resources in terms of memory and network overhead such as in smaller footprint devices, or on a platform where an Ably SDK isn't available such as an Arduino-based IoT wearable. The potential drawback to consider when evaluating protocol adapters is that they do not support the full set of Ably features, for example the MQTT protocol adapter does not support presence, and the SSE protocol adapter does not support automatic token renewal. | ||
|
||
## Migration support <a id="migration-support"/> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
"Migrate to Ably"?
This PR integrates the migrating section of the FAQs into the docs:
Can you help ease the pain of migration from another Data Stream Network?
How does Ably compare with PubNub?
Is it easy to migrate from PubNub to Ably?
Redirects: Here
Jira: EDU-2081
FAQ: Here